Flexible Ethernet over wireless links

ABSTRACT

A mapper includes circuitry configured to receive data streams each or which is a stream of data based on a calendar function associated with one of Flexible Ethernet (FlexE) or Metro Transport Networking (MTN); and circuitry configured to perform mapping of each of the data streams and to provide an output of the mapping to a device in a wireless data plane for transmission over one or more wireless links. The mapping can include packet mapping where the stream of blocks is encapsulated into packets. The mapping can include byte mapping where the stream of blocks is converted into a byte stream that is provided to a Radio Link Control (RLC) layer that guarantees byte delivery in order at a receiver. The mapping can also include bit mapping wherein the stream of blocks is transferred as a stream of bits to a transport buffer Service Access Point (SAP).

FIELD OF THE DISCLOSURE

The present disclosure generally relates to networking. Moreparticularly, the present disclosure relates to systems and methods forFlexible Ethernet (FlexE) over wireless links.

BACKGROUND OF THE DISCLOSURE

Flexible Ethernet (FlexE) is a link multiplexing technology initiallyspecified in the Optical Internetworking Forum's Flexible EthernetImplementation Agreement (document OIF-FLEXE-01.0, March 2016,OIF-FLEXE-01.1, June 2017, and OIF-FLEXE-02.0, June 2018, the contentsof each is incorporated by reference herein). The ImplementationAgreement (IA) enables one or more 100GBASE-R PHYs to be bonded, withclients of 10, 40, and m×25 Gb/s. The bonded 100GBASE-R PHYs are knownas a FlexE Group. Also, MTN (metro transport networking) is beingdeveloped in the International Telecommunication Union (ITU) as G.mtn“Interfaces for a metro transport network.” MTN has also beenhistorically called “Flexible Ethernet (FlexE) switching” or “Slicingpacket Networking (SPN).” FlexE and G.mtn have not been proposed ordescribed for operation over wireless links. That is, FlexE is specifiedfor optical/wired links only utilizing standard IEEE 802.3 EthernetPMDs/PHYs.

There are conventional approaches that utilize a modified Ethernet LinkAggregation Group (LAG) to bond multiple wireless channels. Thisincreases link capacity and reliability. FlexE is advantageous overEthernet LAG as it can support client streams greater than the speed ofthe constituent LAG flows. Also, FlexE does not introduce inefficienciestypically introduced by LAG due to hashing algorithms.

BRIEF SUMMARY OF THE DISCLOSURE

In an embodiment, a mapper includes circuitry configured to receive datastreams each is a stream of data based on a calendar function associatedwith one of Flexible Ethernet (FlexE) and Metro Transport Networking(MTN); and circuitry configured to perform mapping of each of the datastreams and to provide an output of the mapping to a device in awireless data plane for transmission over one or more wireless links.The stream of data can include a stream of blocks sized based on a lineencoding technique. The mapping can include packet mapping where thestream of blocks is encapsulated into packets each having a sequencenumber to ensure correct ordering at a receiver, and the packets can beprovided to the wireless data plane at a Packet Data ConvergenceProtocol (PDCP) layer in the wireless data plane. The mapping caninclude byte mapping where the stream of blocks is converted into a bytestream that is provided to a Radio Link Control (RLC) layer in thewireless data plane that guarantees byte delivery in order at areceiver. The mapping can include bit mapping wherein the stream ofblocks is transferred as a stream of bits to a transport buffer ServiceAccess Point (SAP) in the wireless data plane. The stream of data caninclude a stream of 64 B/66 B blocks, and wherein the data streams areeach about 5 Gb/s corresponding to one of 20 calendar slots in a 100Gb/s FlexE frame. The data streams can be a plurality of streams andeach is transported over portions of different wireless links.

In another embodiment, a system includes a mapper configured to receivedata streams each including a stream of blocks associated with one of aFlexible Ethernet (FlexE) signal or a Metro Transport Networking (MTN)signal, and map the stream of blocks to data formatted for transmissionover one or more wireless links by a transmit device in a wireless dataplane; and a demapper configured to receive the formatted data from areceive device in the wireless data plane, and demap the received datato the stream of blocks reconstituting the one of the FlexE signal andthe MTN signal. The data formatted can include packet mapping where thestream of blocks is encapsulated into packets each having a sequencenumber to ensure correct ordering at the demapper, and the packets caninclude provided to the wireless data plane at a Packet Data ConvergenceProtocol (PDCP) layer in the wireless data plane. The data formatted caninclude byte mapping where the stream of blocks is converted into a bytestream that is provided to a Radio Link Control (RLC) layer in thewireless data plane that guarantees byte delivery in order at thedemapper. The data formatted can include bit mapping wherein the streamof blocks is transferred as a stream of bits to a transport bufferService Access Point (SAP) in the wireless data plane. The stream ofdata can include a stream of 64 B/66 B blocks, and wherein the datastreams are each about 5 Gb/s corresponding to one of 20 calendar slotsin a 100 Gb/s FlexE frame. The data streams can be a plurality ofstreams and each is transported over a different wireless link. Thesystem can further include a transmit buffer between the mapper and thewireless data plane; and a receive buffer between the demapper and thewireless data plane.

In a further embodiment, a method includes receiving data streams eachincluding a stream of blocks associated with one of a Flexible Ethernet(FlexE) stream or a Metro Transport Networking (MTN) stream; and mappingthe stream of blocks to data formatted for transmission over one or morewireless links by a transmit device in a wireless data plane. The methodcan further include receiving the formatted data from a receive devicein the wireless data plane; and demapping the received data to thestream of blocks reconstituting the one of the FlexE signal or the MTNsignal. The data formatted can include packet mapping where the streamof blocks is encapsulated into packets each having a sequence number toensure correct ordering at a receiver, and the packets can be providedto the wireless data plane at a Packet Data Convergence Protocol (PDCP)layer in the wireless data plane. The data formatted can include bytemapping where the stream of blocks is converted into a byte stream thatis provided to a Radio Link Control (RLC) layer in the wireless dataplane that guarantees byte delivery in order at a receiver. The dataformatted can include bit mapping wherein the stream of blocks istransferred as a stream of bits to a transport buffer Service AccessPoint (SAP) in the wireless data plane. The method can further includebuffering the data formatted prior to transmission; and controlling thebuffering based on the one or more wireless links.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated and described herein withreference to the various drawings, in which like reference numbers areused to denote like system components/method steps, as appropriate, andin which:

FIG. 1 is a diagram of the IEEE 802.3 stack and ITU-T architecturalviews of FlexE and MTN;

FIG. 2A is a network diagram of a network illustrating an end-to-endMetro Transport Networking (MTN) circuit utilizing a 5G wireless pointto multi-point link as part of its path;

FIG. 2B is a network diagram illustrating the devices and links of MTNcircuit of FIG. 2A and the IEEE 802.3 stack and ITU-T architecturalviews;

FIG. 3 is a block diagram of a system configured to interface 64 B/66 Bblocks between wireless frames via a mapper between a wired domain and awireless domain;

FIG. 4 is a block diagram of a multi-link wireless network; and

FIG. 5 is a flowchart of a FlexE/MTN transmission process over awireless data plane.

DETAILED DESCRIPTION OF THE DISCLOSURE

The present disclosure relates to systems and methods for FlexibleEthernet (FlexE) over wireless links. The present disclosure substitutesthe lower part of an Ethernet PHY below the FlexE calendar function,with a wireless link. This enables the advantages of a FlexE Group(channelization, bonding, and subrating) to a set of wireless links. Itcan also provide end-to-end hard slicing across multiple different mediatypes (e.g., optical and wireless). The addition of wireless links couldincrease the topology options for Ethernet networks, e.g., topologies ofEthernet links and wireless links could be created. Support of FlexEclients over such topology is beneficial for client rates that do notexactly match the physical rates. Wireless links may be advantageous insome situations where optical fiber is not present or would be expensiveto deploy.

FIG. 1 is a diagram of the IEEE 802.3 stack and ITU-T architecturalviews of FlexE and MTN. The technology enabling FlexE is the FlexE shim,which is an adaptation of a 64 B/66 B encoded bit-stream into a TimeDivision Multiplexing (TDM) like structure across a FlexE group. EachFlexE client has its own bit rate, Media Access Control (MAC), andReconciliation layers, and Media-Independent Interface (xMII) above theFlexE shim. 64 B/66 B blocks from multiple clients are adapted to theFlexE group using a calendar function that distributes them to the100GBASE-R PHYs in the FlexE group. The calendar subdivides each 100Gb/s PHY into 20 slots, and the FlexE shim adaptationmultiplexes/demultiplexes all 64 B/66 B blocks from a FlexE clientinto/from the same set of calendar slots. 200 Gbit/s and 400 Gb/sEthernet PHYs were added in OIF FlexE IA 2.0.

As an example of FlexE, four clients each with a rate of 75 Gb/s, whichis not an IEEE802.3 rate, could be supported by a FlexE group includingthree 100GBASE-R PHYs. The FlexE group acts as a 300 Gb/s Ethernet link.

An emerging technology in ITU-T SG15 called “Metro Transport Network”(MTN) is being standardized as well. It was originally called “SlicingPacket Network,” or SPN. An interface Recommendation G.mtn was startedin Question 11 of SG15 in October 2018. It can be used to accomplish atype of hard network slicing (a type of virtual private networking) forwireless and optical transport applications. MTN adds a switchingfunction to the 64 B/66 B blocks of the FlexE client so that the streamof blocks can traverse FlexE links without having to be adapted back toMAC frames at every hop. FlexE technology only provides big linksbetween Ethernet switches so MAC frames from a FlexE client arere-constituted at every FlexE link hop and may subsequently be forwardedby IEEE802.1 bridging. MTN technology allows the 64 B/66 B blocks of theFlexE client stream to be switched at the egress of a FlexE link. MTNuses FlexE logic for the calendaring and multiplexing/demultiplexingfunctions over the Ethernet PHYs of OIF FlexE IA 2.0.

MTN has a path layer and a section layer. The path layer includes aswitching function from which a path layer network can be formed. InFIG. 1, the FlexE client stream of blocks is present at the PathForwarding End Point (FwEP). For the OIF FlexE case, there is noflexibility to switch the blocks from the Path FwEP, and they are boundto Path Forwarding Points (“Path FP”). Below the Path FPs, the FlexEshim and calendaring function are performed, and 64 B/66 B blocks areplaced into 5 Gbit/s calendar slots.

The bonding of links to form a higher aggregate rate is a general methodfound across packet and TDM technologies. Bonding of wireless links alsoexists. While the use of Ethernet LAG is known for wireless links, theuse of FlexE is not. In this invention, wireless links thatmodulate/demodulate 64 B/66 B encoded bit-streams are bonded using theOIF FlexE shim and adaptation. These wireless bonded links must use thesame physical layer clock. 64 B/66 B blocks at the Path FwEP in theabove diagram would flow to the FlexE calendaring function and FlexEclients multiplexed using the FlexE shim.

64 B/66 B is a line code that transforms 64-bit data to a 66-bit blockto provide enough state changes to allow reasonable clock recovery andalignment of the data stream at the receiver. 64 B/66 B was defined bythe IEEE 802.3 working group as part of the IEEE 802.3ae-2002 amendmentwhich introduced 10 Gbit/s Ethernet, the contents of which areincorporated by reference. An output of 64 B/66 B encoding is a 66 Bblock. As described herein, FlexE and MTN include a stream of blockswhich can be referred to herein as 64 B/66 B block streams or a streamof 66 B blocks.

The various embodiments described herein are with reference to 64/66 Bblocks, which is an output of 64/66 B encoding. That is, the 66 B blockis a block of bits based on a line code, which in this case is 64/66 Bencoding. There are other types of line codes, and the presentdisclosure equally contemplates use therein with respect to FlexE orMTN. For example, another type of line code is 256 B/257 B encoding.Here, 256 bits of data are encoded into 257 B blocks. It is expectedthat FlexE or MTN may also support 256 B/257 B blocks in addition to 64B/66 B blocks.

In the present disclosure, instead of continuing to the rest of the IEEE802.3 clause 82 stack and below (Physical Medium Attachment (PMA),Physical Medium Dependent (PMD)), the stream would go to wireless linkscapable of modulating/demodulating 64 B/66 B blocks. This would be belowthe Section Forwarding Endpoint (FwEP). The foregoing description ispresented with respect to 64 B/66 B blocks for FlexE or MTN. Those ofordinary skill in the art will appreciate the present disclosurecontemplates any types of blocks for FlexE or MTN for transmission overwireless links.

As wireless links are subject to factors (e.g., atmospheric, spacial)that can cause their bit rate to vary, links with a Guaranteed Bit Rate(GBR) service should be used at the Section Forwarding EndPoint (FwEP).If not available, then a mechanism to provide a constant bit rate to theFlexE calendaring function is needed. This mechanism could beimplemented with a leaky bucket and a queueing buffer. The FlexE idlemapped procedure can be utilized to subrate and match the GBR to theappropriate resource (slice). For example, a buffer between thecalendaring function and the wireless link.

The present disclosure applies to the case where FlexE links are used(the OIF IAs) as well as for the MTN case where there the 64 B/66 Bblock stream can be switched.

FIG. 2A is a network diagram of a network 10 illustrating an end-to-endMTN circuit 12 utilizing a 5G wireless point to multi-point link 14 aspart of its path. The network 10 includes connectivity of the end-to-endMTN path connection 12 between an Ethernet switch 16 and a networkdevice 18. The 5G wireless point to multi-point link 14 includes celltower 20 at the point that is wirelessly connected to one or moremicrowave devices 22 at the multipoint. The end-to-end MTN circuit 12traverses over multiple 5G wireless links 36. The 5G wireless links 36can be bookended by edge devices 24, 26 and corresponding VirtualNetwork Functions (VNFs) 28, 30. For example, the VNF 28 can be anevolved Node B (eNB) or gNodeB (gNB) and the VNF 30 can be UserEquipment (UE). We are also contemplating other ways to implement theVNF functionality, including with hardware based wireless transmittingpoints (TPs) such as hardware eNBs, gNBs, 802.11 wireless access points,802.11 wireless routers, 802.11 mesh routers, satellite terrestrialtransmitters and satellite relays, and hardware UEs (e.g. cellularphones or cellular modems). Further, the network 10 can include an MTNcontroller 32 with control connectivity to the Ethernet switch 16, thenetwork device 18, edge devices 24, 26, and corresponding VirtualNetwork Functions (VNFs) 28, 30. A 5G controller 34 also has controlconnectivity to the MTN controller 32. The MTN controller 32 isconfigured to provision the FlexE calendar in the devices it has controlconnectivity to, and the 5G controller is configured to provisionQuality of Service (QoS).

FlexE or MTN Path client data may originate at Ethernet switch 16, beswitched over a FlexE group over optical Ethernet links, and arrives atthe edge device 24. Then, it is switched in the MTN path layer to anegress microwave links 36 in the 5G wireless point to multi-point link14. FlexE or MTN path client data at the output of the microwave link 36is switched to an egress FlexE group over optical Ethernet links 38. Theend-to-end MTN path connection 12 is configured by setting up calendarslots on the Ethernet switch 16, the network device 18, and the edgedevices 24 and 26 respectively, and setting up calendar slots withwireless QoS requirements on the microwave link 36.

In FIG. 2A, the example end-to-end MTN path connection 12 is illustratedtraversing the 5G wireless point to multi-point link 14. Of course,other embodiments are also contemplated. The end-to-end MTN circuit 12includes FlexE, i.e., a 64 B/66 B block stream that is distributed basedon the calendar. FIG. 2B depicts the devices and links that the MTN pathconnection 12 of FIG. 2 in a simplified system 100. A correspondingfunctional architecture is given in 101. The MTN Path connection 12 (ofFIG. 2A) would start at the Ethernet switch 16, is adapted to the MTNPath layer in 110, then enters the MTN switching function 120 which wasprovisioned by the MTN Controller 32 (of FIG. 2A). It is switched to theMTN Section layer 130 which contains the calendar mapping function. 64B/66 B blocks are distributed to calendar slots in the PCS and lowerfunctions of Ethernet PHYs 140 as described in [0012]. The 64 B/66 Bblock stream of the FlexE or MTN path client is bonded over two EthernetPHYs and modulated over optical fibres 150. At the receiving end ondevice 24, the data is demodulated and the calendaring function of theMTN Section layer recovers the 64 B/66 B block stream of the MTN Pathconnection 12 (of FIG. 2A). The MTN Path switching function 121 isconfigured by MTN controller 32 to send the stream to the MTN Sectionlayer 131. The calendar mapping function distributes 64 B/66 B blocks tocalendar slots in the wireless link functions 141 prior to wirelessmodulation. The 64 B/66 B block stream is the data lane stream 64 (ofFIG. 3) which for this example is sent by the data plane to wirelessdata plane mapper 50 (of FIG. 3) to the transport buffer creation 74 (ofFIG. 3) function as a bit stream. The bits are then sent to a wirelessmodulation function and transmitted. The 64 B/66 B block stream of theFlexE or MTN path client is bonded over two wireless PHYs and modulatedover wireless links 151. At the receiving end, on device 26, the data isdemodulated and the calendaring function of the MTN Section layerrecovers the 64 B/66 B block stream of the MTN Path connection 12 (ofFIG. 2A). The MTN Path switching function 122 is configured by MTNcontroller 32 to send the stream to the MTN Section layer that bonds itover two Ethernet PHYs which are modulated over optical fibres 152. Atthe receiving end, on device 18, the data is demodulated and thecalendaring function of the MTN Section layer recovers the 64 B/66 Bblock stream of the MTN Path connection 12 (of FIG. 2A). The MTN Pathswitching function 123 is configured by MTN controller 32 to send thestream to the MTN Path layer 111 which outputs MAC frames from the 64B/66 B block stream. This is the end of the MTN Path connection 12.

A wireless resources scheduler, such as via the 5G controller 34, can beconfigured to schedule the data from this bit stream in a way thatachieves its required quality of service over the wireless links 151 (ofFIG. 3). The end-to-end path is set up by setting up scheduling calendarslots on the ethernet devices and setting up wireless QoS requirementsby the MTN controller 32.

FIG. 3 is a block diagram of a system 40 configured to interface 64 B/66B blocks between wireless frames via a mapper 50 between a wired domain52 and a wireless domain 54.

Within the edge devices 24, 26 that originate/terminate the microwavelinks 36, a FlexE calendar function 60, in a calendar mapper 62, maps 64B/66 B blocks into a FlexE frame that is used to allocate 64 B/66 Bblocks to sub-calendars for each of the microwave links 36, to data lanestreams 64 that interface the mapper 50. For a 100 Gb/s PHY, eachsub-calendar can have a granularity of 5 Gb/s, i.e., 20 calendar slots.The data lane streams 64 are streams of FlexE client data (or MTN pathlayer clients), namely a stream of 64 B/66 B blocks. For example, thedata lane streams can be equal to the sub-calendar, e.g., 5 Gb/s. Again,20 calendar slots of 5 Gb/s each is currently standardized for FlexE,but it is expected that there will be different rates in the future.These future rates are also contemplated with the present disclosure.

The wireless domain 54 includes a Packet Data Convergence Protocol(PDCP) mapper 70 that interfaces a Radio Link Control (RLC) layer 72that interfaces a transport buffer 74. The transport buffer 74 connectsto a modulation device 76 that connects to a spectrum resource mapper 78that supports wireless transmission. FIG. 3 is illustrated in a singledirection, transmission from left to right. Of course, a practicalembodiment with bidirectional communication would support the samefunctions in both directions.

The PDCP mapper 70 encapsulates data into an IP packet (among otherfunctions) that are wireless domain datagrams. The RLC layer 72 providesbuffering of bytes to match an incoming data stream with the wirelesschannel and reliable transmission of bytes over the wireless channel(layer 2 functionalities). The transport buffer 74 function performs i)layer 1 wireless functionality and hybrid Automatic Repeat Request (ARQ)to deal with fading channels, ii) creation of buffers of coded bitscreated in a size that can be mapped on available spectrum and timeresources (Orthogonal Frequency-Division Multiplexing (OFDM) symbols),iii) coding such as Low-Density Parity-Check (LDPC), polar, TurboProduct Code (TPC) (some bits may be removed from the coded buffer tocreate punctured codes), and iv) the like. The modulation device 76includes creating symbols (time waveforms) from coded bits. The spectrumresource mapper 78 may work with modulation to assign bits to wirelessspectrum or in time (on OFDMA symbols or resource blocks).

The mapper 50 can be referred to as a “data lane to wireless data planemapper” to perform adaptation between the wired domain 52 and thewireless domain 54. In the present disclosure, there are three proposedapproaches for how a wireless system can transport the 64 B/66 B blockstreams. These include transport by bits, by bytes, or by encapsulationin IP packets; these are referred to herein as bit mapping, bytemapping, and packet mapping, respectively. 64 B/66 B streams are takenoff the data lane streams 64 and are handed off to some part of thewireless data plane by the mapper 50. Depending on where they are handedoff, i.e., the approach, different type of mapping/encapsulations arerequired. The description in [0024] uses the bit mapping.

For packet mapping, the mapper 50 provides the 64 B/66 B data stream tothe PDCP mapper 70 via IP encapsulation. The mapper 50 can pack a 64B/66 B block stream into IP packets or the like, i.e., something thatcan be transported over the wireless stack. IP encapsulation can includesequence numbers in the packets to ensure the 64 B/66 B block stream canbe reconstituted in the correct order at the receiver, i.e., at anadjacent mapper 50 on the other end of the wireless domain 54.

For byte mapping, the 64 B/66 B block stream can be converted into abyte stream, e.g., four 66 B blocks can become a 33-byte stream, and thebyte stream can be provided to the RLC layer 72 using its byte ServiceAccess Point (SAP). The RLC layer 72 provides guaranteed byte deliveryso all bytes will be received in order at the receiver.

For bit mapping, the 64 B/66 B block stream can be transferred as is asa stream of bits to the transport buffer 74 SAP. Even further, thisoption could include packing the stream of bits with a header andpadding to match available transport buffer 74 sizes to enable trackingof lost 66 B blocks.

FIG. 4 is a block diagram of a multi-link wireless network 100 with aplurality of wireless links 102. As the bandwidth on a wireless link 102is affected by atmospheric and other factors, a necessary condition forits use in a FlexE group is that there be a minimum guaranteedbandwidth. Use of a Guaranteed Bit Rate (GBR) service could be used.Wireless spectrum is shared by multiple wireless links 102, and eachlink may have a different Signal-to-Interference-Plus-Noise Ratio(SINR). Wireless spectrum may be used as multiple spatial channels, eachwith a different SINR.

In order to provide a GBR service, the scheduler (such as in the MTNcontroller 32) needs to schedule all GBR packets/bytes/bits (dependingon the mapping 50 used) before all other packets/bytes/bits to ensurethat sufficient resources are reserved for the MTN traffic. The minimumrequired bandwidth required by the MTN traffic has to be available onthe wireless link 102. The minimum bandwidth can be determined by a sumof the lowest Modulation and Coding Scheme (MCS) on each spatial channelif that channel is using the full spectrum available on the link 102.

The transmit buffer 74 is required because each link 102 may have adifferent rate. Sometimes the aggregate rate may be smaller than theFlexE rate. A receive buffer 104 is required because each link 102 mayhave a different, variable, latency (due to ARQ). The receive buffer 104orders packets/bytes/bits to be able to give them back to the FlexEstream. The mapper 50 reads the calendar and packs packets/bytes/bitsinto wireless links. The MTN controller 32 can be an outside entity thatis required to assign which part of FlexE calendar is using whichwireless links 102 (if multiple FlexE flows can be packed on thewireless FlexE group).

FIG. 5 is a flowchart of a FlexE/MTN transmission process 200 over awireless data plane. The process 200 includes receiving data lanestreams each including a stream of blocks associated with one of aFlexible Ethernet (FlexE) stream or a Metro Transport Networking (MTN)stream (step S1); and mapping the stream of blocks to data formatted fortransmission over one or more wireless links by a transmit device in awireless data plane (step S2).

The process 200 can further include receiving the formatted data from areceive device in the wireless data plane (step S3); and demapping thereceived data to the stream of blocks reconstituting the one of theFlexE stream or the MTN stream (step S4).

The data formatted can include packet mapping where the stream of blocksis encapsulated into packets each having a sequence number to ensurecorrect ordering at the demapper, and wherein the packets are providedto the wireless data plane at a Packet Data Convergence Protocol (PDCP)layer in the wireless data plane.

The data formatted can include byte mapping where the stream of blocksis converted into a byte stream that is provided to a Radio Link Control(RLC) layer in the wireless data plane that guarantees byte delivery inorder at the demapper.

The data formatted can include bit mapping wherein the stream of blocksis transferred as a stream of bits to a transport buffer Service AccessPoint (SAP) in the wireless data plane.

The process 200 can further include buffering the data formatted priorto transmission; and controlling the buffering based on the one or morewireless links.

In another embodiment, a mapper includes circuitry configured to receivedata lane streams each of which is a stream of data based on a calendarfunction associated with one of Flexible Ethernet (FlexE) or MetroTransport Networking (MTN); and circuitry configured to perform mappingof each of the data streams and to provide an output of the mapping to adevice in a wireless data plane for transmission over one or morewireless links.

The stream of data can include a stream of blocks sized based on a lineencoding technique. The mapping can include packet mapping where thestream of blocks is encapsulated into packets each having a sequencenumber to ensure correct ordering at a receiver, and wherein the packetsare provided to the wireless data plane at a Packet Data ConvergenceProtocol (PDCP) layer in the wireless data plane.

The mapping can include byte mapping where the stream of blocks isconverted into a byte stream that is provided to a Radio Link Control(RLC) layer in the wireless data plane that guarantees byte delivery inorder at a receiver. The mapping can include bit mapping wherein thestream of blocks is transferred as a stream of bits to a transportbuffer Service Access Point (SAP) in the wireless data plane. The streamof data can include a stream of 64 B/66 B blocks, and wherein the datalane streams are each about 5 Gb/s corresponding to one of 20 calendarslots in a 100 Gb/s FlexE frame. The data lane streams can be aplurality of streams, and each is transported over a different wirelesslink.

In a further embodiment, a system includes a mapper configured toreceive data lane streams each including a stream of blocks associatedwith one of a Flexible Ethernet (FlexE) signal or a Metro TransportNetworking (MTN) signal, and map the stream of blocks to data formattedfor transmission over one or more wireless links by a transmit device ina wireless data plane; and a demapper configured to receive theformatted data from a receive device in the wireless data plane, anddemap the received data to the stream of blocks reconstituting the oneof the FlexE signal or the MTN signal.

It will be appreciated that some embodiments described herein mayinclude one or more generic or specialized processors (“one or moreprocessors”) such as microprocessors; Central Processing Units (CPUs);Digital Signal Processors (DSPs): customized processors such as NetworkProcessors (NPs) or Network Processing Units (NPUs), Graphics ProcessingUnits (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); andthe like along with unique stored program instructions (including bothsoftware and firmware) for control thereof to implement, in conjunctionwith certain non-processor circuits, some, most, or all of the functionsof the methods and/or systems described herein. Alternatively, some orall functions may be implemented by a state machine that has no storedprogram instructions, or in one or more Application Specific IntegratedCircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic or circuitry. Ofcourse, a combination of the aforementioned approaches may be used. Forsome of the embodiments described herein, a corresponding device inhardware and optionally with software, firmware, and a combinationthereof can be referred to as “circuitry configured or adapted to,”“logic configured or adapted to,” etc. perform a set of operations,steps, methods, processes, algorithms, functions, techniques, etc. ondigital and/or analog signals as described herein for the variousembodiments.

Moreover, some embodiments may include a non-transitorycomputer-readable storage medium having computer readable code storedthereon for programming a computer, server, appliance, device,processor, circuit, etc. each of which may include a processor toperform functions as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, an optical storage device, a magnetic storage device, a ROM(Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM(Erasable Programmable Read Only Memory), an EEPROM (ElectricallyErasable Programmable Read Only Memory), Flash memory, and the like.When stored in the non-transitory computer-readable medium, software caninclude instructions executable by a processor or device (e.g., any typeof programmable circuitry or logic) that, in response to such execution,cause a processor or the device to perform a set of operations, steps,methods, processes, algorithms, functions, techniques, etc. as describedherein for the various embodiments.

Although the present disclosure has been illustrated and describedherein with reference to preferred embodiments and specific examplesthereof, it will be readily apparent to those of ordinary skill in theart that other embodiments and examples may perform similar functionsand/or achieve like results. All such equivalent embodiments andexamples are within the spirit and scope of the present disclosure, arecontemplated thereby, and are intended to be covered by the followingclaims.

What is claimed is:
 1. A mapper comprising: circuitry configured toreceive data streams each is a stream of data based on a calendarfunction associated with one of Flexible Ethernet (FlexE) and MetroTransport Networking (MTN); and circuitry configured to perform mappingof each of the data streams and to provide an output of the mapping to adevice in a wireless data plane for transmission over one or morewireless links.
 2. The mapper of claim 1, wherein the stream of dataincludes a stream of blocks sized based on a line encoding technique. 3.The mapper of claim 2, wherein the mapping includes packet mapping wherethe stream of blocks is encapsulated into packets each having a sequencenumber to ensure correct ordering at a receiver, and wherein the packetsare provided to the wireless data plane at a Packet Data ConvergenceProtocol (PDCP) layer in the wireless data plane.
 4. The mapper of claim2, wherein the mapping includes byte mapping where the stream of blocksis converted into a byte stream that is provided to a Radio Link Control(RLC) layer in the wireless data plane that guarantees byte delivery inorder at a receiver.
 5. The mapper of claim 2, wherein the mappingincludes bit mapping wherein the stream of blocks is transferred as astream of bits to a transport buffer Service Access Point (SAP) in thewireless data plane.
 6. The mapper of claim 1, wherein the stream ofdata includes a stream of 64 B/66 B blocks, and wherein the data streamsare each about 5Gb/s corresponding to one of 20 calendar slots in a 100Gb/s FlexE frame.
 7. The mapper of claim 1, wherein the data streams area plurality of streams and each is transported over portions ofdifferent wireless links.
 8. A system comprising: a mapper configured toreceive data streams each including a stream of blocks associated withone of a Flexible Ethernet (FlexE) signal or a Metro TransportNetworking (MTN) signal, and map the stream of blocks to data formattedfor transmission over one or more wireless links by a transmit device ina wireless data plane; and a demapper configured to receive theformatted data from a receive device in the wireless data plane, anddemap the received data to the stream of blocks reconstituting the oneof the FlexE signal and the MTN signal.
 9. The system of claim 8,wherein the data formatted includes packet mapping where the stream ofblocks is encapsulated into packets each having a sequence number toensure correct ordering at the demapper, and wherein the packets areprovided to the wireless data plane at a Packet Data ConvergenceProtocol (PDCP) layer in the wireless data plane.
 10. The system ofclaim 8, wherein the data formatted includes byte mapping where thestream of blocks is converted into a byte stream that is provided to aRadio Link Control (RLC) layer in the wireless data plane thatguarantees byte delivery in order at the demapper.
 11. The system ofclaim 8, wherein the data formatted includes bit mapping wherein thestream of blocks is transferred as a stream of bits to a transportbuffer Service Access Point (SAP) in the wireless data plane.
 12. Thesystem of claim 8, wherein the stream of data includes a stream of 64B/66 B blocks, and wherein the data streams are each about 5 Gb/scorresponding to one of 20 calendar slots in a 100 Gb/s FlexE frame. 13.The system of claim 8, wherein the data streams are a plurality ofstreams and each is transported over a different wireless link.
 14. Thesystem of claim 8, further comprising a transmit buffer between themapper and the wireless data plane; and a receive buffer between thedemapper and the wireless data plane.
 15. A method comprising: receivingdata streams each including a stream of blocks associated with one of aFlexible Ethernet (FlexE) stream or a Metro Transport Networking (MTN)stream; and mapping the stream of blocks to data formatted fortransmission over one or more wireless links by a transmit device in awireless data plane.
 16. The method of claim 15, further comprisingreceiving the formatted data from a receive device in the wireless dataplane; and demapping the received data to the stream of blocksreconstituting the one of the FlexE signal or the MTN signal.
 17. Themethod of claim 15, wherein the data formatted includes packet mappingwhere the stream of blocks is encapsulated into packets each having asequence number to ensure correct ordering at a receiver, and whereinthe packets are provided to the wireless data plane at a Packet DataConvergence Protocol (PDCP) layer in the wireless data plane.
 18. Themethod of claim 15, wherein the data formatted includes byte mappingwhere the stream of blocks is converted into a byte stream that isprovided to a Radio Link Control (RLC) layer in the wireless data planethat guarantees byte delivery in order at a receiver.
 19. The method ofclaim 15, wherein the data formatted includes bit mapping wherein thestream of blocks is transferred as a stream of bits to a transportbuffer Service Access Point (SAP) in the wireless data plane.
 20. Themethod of claim 15, further comprising buffering the data formattedprior to transmission; and controlling the buffering based on the one ormore wireless links.